* **Simplify the modified header rule.** The new `(\s*\S*\s*\S*)` group extends the match by at most two trailing tokens,

This was designed to match the "Port Cross Connect 1" text and still be backwards compatible with two-word port names.

Port Descriptions on Port Cross Connect 1

so a header like Port Descriptions on Card 1 Module 2 Foo Bar would still fail to match. \s+.+ matches any trailing content and reads more clearly; tests pass locally with this change.

There are more words in the foo bar example than we see in actual output.

Nothing wrong with some simplification. ❤️
Maybe we don't even need to anchor on the end of the line?

(So instead of the first two, just the last one in green.)

-  ^Port\s+Descriptions\s+on\s\S+\s+\S+(\s*\S*\s*\S*)\s*$$ 
-  ^Port\s+Descriptions\s+on\s+.+$$
+  ^Port\s+Descriptions\s+on

Thank you for the review

I think that will work as well. Update and I'll approve.
I ran it through my AI reviewer and it confirmed, explaining why:

Thanks @mjbear — the multiline-description handling and the new fixture look great, and tests pass cleanly. One suggestion before merge:

• Simplify the header rule. The (\s*\S*\s*\S*) group only buys two extra trailing tokens, so a longer header label would still slip through, and it's a bit hard to read. Since this rule just discards the header line (no Value is captured from it), it can match on the stable prefix instead — which is the form you proposed in the thread. I confirmed all tests still pass with it.

  In ntc_templates/templates/alcatel_sros_show_port_description.textfsm, the header rule in Start:

  -  ^Port\s+Descriptions\s+on\s\S+\s+\S+(\s*\S*\s*\S*)\s*$$ 
  +  ^Port\s+Descriptions\s+on

I think that will work as well. Update and I'll approve.
I ran it through my AI reviewer and it confirmed, explaining why:

This pattern has been there since inception via PR #1912 - makes sense to adjust/simplify it.

I've updated the port description pattern in the template.